Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarLint
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarCloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube

Secrets
ABAP
Ansible
Apex
AzureResourceManager
C
C#
C++
CloudFormation
COBOL
CSS
Dart
Docker
Flex
Go
HTML
Java
JavaScript
JCL
Kotlin
Kubernetes
Objective C
PHP
PL/I
PL/SQL
Python
RPG
Ruby
Scala
Swift
Terraform
Text
TypeScript
T-SQL
VB.NET
VB6
XML

VB6 static code analysis

Unique rules to find Bugs, Security Hotspots, and Code Smells in your VB6 code

Tags

Impact

Clean code attribute

"Option Base" should not be used
Code Smell
The "&" operator should be used to concatenate strings
Code Smell
"Select" statements should end with a "Case Else" clause
Code Smell
Methods should not be empty
Code Smell
Constant names should comply with a naming convention
Code Smell
"GoTo" statements should not be used
Code Smell
Variable data types should be declared explicitly
Code Smell
The bang ("!") operator should not be used
Code Smell
"Asc[W]" should not be called on string constants
Code Smell
"Chr[W]$()" should not be used for certain characters
Code Smell
String-specific functions should be used
Code Smell
Strings should not be compared with empty string
Code Smell
Sub and function names should comply with a naming convention
Code Smell
"Select Case" statements should not have too many "Case" clauses
Code Smell
Track uses of "FIXME" tags
Code Smell
Nested blocks of code should not be left empty
Code Smell
Procedures should not have too many parameters
Code Smell
Unused private variables should be removed
Code Smell
Multiple variables should not be declared on the same line
Code Smell
"Select Case" statements should have at least 3 "Case" clauses
Code Smell
Return of boolean expressions should not be wrapped into an "if-then-else" statement
Code Smell
Boolean literals should not be redundant
Code Smell
Empty statements should be removed
Code Smell
Track uses of "TODO" tags
Code Smell
"Select Case" statements should not be nested
Code Smell
Subs and functions should not be too complex
Code Smell
Expressions should not be too complex
Code Smell
Track parsing failures
Code Smell
Loop invariants should not be calculated inside the loop
Code Smell
Strings should not be set to empty string
Code Smell
Subs and functions should not have too many lines
Code Smell
Statements should be on separate lines
Code Smell
"Case" clauses should not have too many lines
Code Smell
Magic numbers should not be used
Code Smell
Files should not have too many lines of code
Code Smell
Lines should not be too long
Code Smell
'$' should not be used in string variable names
Code Smell
Comments should not be located at the end of lines of code
Code Smell
Lines should not end with trailing whitespaces
Code Smell
Source code should be indented consistently
Code Smell
Tabulation characters should not be used
Code Smell

"Select Case" statements should not have too many "Case" clauses

adaptability - focused

maintainability

Code Smell

MajorSonarSource default severity
click to learn more

brain-overload

Why is this an issue?

When Select Case statements have a large set of Case clauses, it is usually an attempt to map two sets of data.

A real map structure would be more readable and maintainable, and should be used instead.

Available In:

Enterprise
Edition

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Sonar helps developers write Clean Code.
Privacy Policy | Cookie Policy

In-IDE

SaaS

Self-Hosted